Method and system for supporting fast recovery of user equipment

ABSTRACT

A method for supporting fast recovery of a User Equipment (UE) includes performing, by a serving base station, UE context synchronization for one or more other base stations in a related small cell cluster when a UE accesses the serving base station, performing, by a base station that the UE performs a radio resource control (RRC) connection re-establishment, the RRC connection re-establishment for the UE according to UE context saved in a synchronization process. The present also discloses another method and system for supporting UE fast recovery. By applying the technical solution disclosed by the present disclosure, when the UE moves in a small cell scenario, the UE can be recovered quickly in the case of a failure, so as to avoid the UE returns to an idle mode, avoid data loss, guarantee business continuity, and improve UE experience.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/254,447 filed on Jan. 22, 2019, which is a continuation ofU.S. patent application Ser. No. 16/140,321 filed on Sep. 24, 2018 nowU.S. Pat. No. 10,368,273 issued on Jul. 30, 2019, which is acontinuation of U.S. patent application Ser. No. 14/140,253 filed onDec. 24, 2013 now U.S. Pat. No. 10,136,365 issued on Nov. 20, 2018,which is based on and claims priority under 35 U.S.C. § 119 to ChinesePatent Application No. 201210567595.X filed on Dec. 24, 2012, ChinesePatent Application No. 201310512150.6 filed on Oct. 25, 2013 and ChinesePatent Application No. 201310552962.3 filed on Nov. 8, 2013 in the StateIntellectual Property Office, the disclosures of which are hereinincorporated by reference in their entirety.

BACKGROUND 1. Field

The present disclosure relates to wireless communication technology, andmore particularly, to a method for supporting UE fast recovery.

2. Description of Related Art

Modern mobile communication tends to be more to provide multimediaservices with high-speed transmission. FIG. 1 is a schematic diagramillustrating a structure for a system of system architecture evolution(SAE).

A user equipment (UE) 101 is a terminal device used to receive data. Anevolved universal terrestrial radio access network (E-UTRAN) 102 is awireless access network, which includes a macro base station(eNodeB/NodeB) providing an interface for the UE to access the wirelessnetwork. A mobility management entity (MME) 103 is responsible formanaging mobility context, session context and security information ofthe UE. A service gateway (SGW) mainly provides a user-plane function.The MME 103 and the SGW 104 may be deployed in a same physical entity. Apacket data network gateway (PGW) 105 is responsible for functions suchas charging, lawful monitoring and so on, also may be deployed in a samephysical entity with the SGW 104. A policy and charging rule functionalentity (PCRF) 106 provides a principle of quality of service (QoS) and acharging rule. A Serving GPRS Support Node (SGSN) 108 is a network nodedevice, which provides routing for data transmission in Universal MobileTelecommunications System (UMTS). A Home Subscriber Server (HSS) 109 isa home sub-system of the UE, which is responsible for protecting userinformation such as a current position, an address of a service node,user security information, packet data context of the user equipment andso on.

A small cell enhancement requirement is provided in 3GPP Release 12(Rel-12). As shown in FIG. 2, target scenarios of small cell enhancementinclude a scenario with macro cell coverage and a scenario without themacro cell coverage, an indoor scenario and an outdoor scenario, ascenario with an ideal backhaul and a scenario with a non-idealbackhaul.

In a condition with the macro cell coverage, a carrier aggregationtechnology is provided, which is applied among different base stations.A macro cell and a small cell may work on different frequency bands. Ina condition without the macro cell coverage, there is no a specificsolution how to enhance small cell performance.

SUMMARY

To address the above-discussed deficiencies, it is a primary object toprovide a method for supporting UE fast recovery. When a UE moves in asmall cell scenario, the UE can be recovered quickly in the case of afailure, so as to avoid the UE returns to an idle mode, avoid data loss,guarantee service continuity, and improve UE experience.

The present disclosure provides a method for supporting UE fastrecovery, which includes: A) performing, by a serving base station, UEcontext synchronization for one or more other base stations in a smallcell cluster of the serving base station when a UE accesses the servingbase station; B) performing, by a base station that the UE performs aradio resource control (RRC) connection re-establishment, the RRCconnection re-establishment for the UE according to UE context saved ina synchronization process.

Preferably, the UE accesses the serving base station includes: the UEchanges from an idle mode to an active mode in a cell of the servingbase station; and performing, by a serving base station, UE contextsynchronization for one or more base stations in a small cell cluster ofthe serving base station comprises transmitting, by the serving basestation, the UE context of the UE to the one or more base stations in asmall cell cluster of the serving base station, saving, by the one ormore base stations, the UE context.

Preferably, the method further includes: transmitting, by the servingbase station, updated UE context to the one or more base stations in thesmall cell cluster of the serving base station, saving, by the one ormore base stations, the updated UE context when the UE context needs tobe updated; transmitting, by the serving base station, a message ofreleasing the UE context to a corresponding base station in the smallcell cluster of the serving base station, releasing, by thecorresponding base station, corresponding UE context when the UE returnsto the idle mode from the active mode in the cell of the serving basestation, or when the UE moves out of the cell of the serving basestation, or when the UE moves out of the cell of the serving basestation and a target cell is not in the small cell cluster of theserving base station.

Preferably, the UE accesses the serving base station comprises the UEaccesses the cell of the serving base station through handover; andperforming, by a serving base station, UE context synchronization forone or more other base stations in a small cell cluster of the servingbase station comprises synchronizing the UE context to a base station ina target small cell cluster, and releasing the UE context in a basestation in a source small cell cluster; wherein the source small cellcluster refers to the small cell cluster of the source base station; thetarget small cell cluster refers to a small cell cluster of a targetbase station.

Preferably, before the A, the method further includes: exchanging, by afirst base station and a second base station, information of small cellclusters during a process of establishing an X2; or exchanging, by thefirst base station and the second base station, the information of thesmall cell clusters through a core network via an S1 interface; orbroadcasting, by the first base station, the information of a small cellcluster of the first base station, obtaining, by the UE, the informationof the small cell cluster of the first base station from broadcastinformation of the first base station, and transmitting the informationof the small cell cluster of the first base station to the second basestation; or exchanging, by the first base station and the second basestation, the information of the small cell clusters during an X2handover process; or exchanging, by the first base station and thesecond base station, the information of the small cell clusters duringan S1 handover process; wherein the information of a small cell clusterrefers to a identifier of the small cell cluster of one or more basestations or a list of the one or more base stations in the small cellcluster of the one or more base station, the list of the one or morebase stations refers to a list of one or more base station identifiers,or a list of one or more base station IP addresses, or a list ofinformation that may identify the one or more base stations.

Preferably, synchronizing the UE context to a base station in a targetsmall cell cluster, and releasing the UE context in a base station in asource small cell cluster includes three ways: a first way is:transmitting, by the target base station, the UE context to one or moreother base stations in the target small cell cluster, saving, by the oneor more other base stations, the UE context; transmitting, by the sourcebase station, the message of releasing the UE context to the basestation in the source small cell cluster, releasing, by the one or moreother base stations, corresponding UE context; a second way is:updating, by the target base station, the UE context for a base stationin both the source small cell cluster and in target small cell cluster;transmitting, by the target base station, the UE context to a basestation in the target small cell cluster but not in the source smallcell cluster; transmitting, by the source base station, the message ofreleasing the UE context to a base station in the source small cellcluster but not in the target small cell cluster; a third way is:updating, by the target base station, the UE context for the basestation in both the small cell cluster and the target small cellcluster; transmitting, by the target base station, the UE context to thebase station in the target small cell cluster but not in the sourcesmall cell cluster; transmitting, by the target base station, themessage of releasing the UE context to the base station in the sourcesmall cell cluster but not in the target small cell cluster.

Preferably, obtaining, by the source base station of the UE, the one ormore other base stations in the small cell cluster of the source basestation include: obtaining, by the source base station, the one or moreother base stations in the small cell cluster of the source base stationaccording to configuration information; or taking, by the source basestation, one or more base stations around a cell accessed by the UEcurrently as the one or more base stations in the small cell cluster ofthe source base station according to the cell accessed by the UEcurrently; or determining, by the source base station, one or more basestations of one or more small cells around according to a measurementreport of the UE, taking the one or more other base stations as the oneor more base stations in the small cell cluster of the source basestation according to a measurement report of the UE; obtaining, by thesource base station, a group of small cells according to theconfiguration information, filtering the configured group of the smallcells according to the measurement report of the UE, obtaining the oneor more other base stations in the small cell cluster of the source basestation.

Preferably, the UE context includes a cell identifier of the cellaccessed by the UE in the source base station and an identifier of theUE in the cell accessed by the UE; the UE context further includes oneor more kinds of information as follows: UE security context, ERABinformation, source MME information, an identifier of the UE in a sourceMME, UE capability, a handover limitation list, UE history information.

The present disclosure provides another method for supporting UE fastrecovery, which includes: transmitting, by a UE, a RRC re-establishmentrequest message to a second base station; requesting, by the second basestation, UE context to a first base station, wherein the first basestation is a serving base station before the failure occurs for the UE;transmitting, by the first base station, the UE context of the UE to thesecond base station; and performing, by the second base station, a RRCconnection re-establishment according to the received UE context.

Preferably, the UE context includes a cell identifier of the cell wherethe failure occurs for the UE and an identifier of the UE in the cellwhere the failure occurs for the UE; the UE context further includes oneor more kinds of information as follows: UE security context, ERABinformation, source MME information, an identifier of the UE in a sourceMME, UE capability, a handover limitation list, UE history information.

Preferably, the method further includes: performing, by the first basestation or the second base station, security check.

Preferably, the method further includes: performing, by the first basestation or the second base station, access check.

It can be seen from the above technical solution that when the UE movesin the small cell scenario, the method for supporting UE fast recoveryprovided by the present disclosure causes that the base station in therelated small cell cluster can obtain the UE context by taking differentmethods. Thus, when a failure occurs for the UE and the UE performs theRRC connection re-establishment, the base station that the UE performsthe RRC connection re-establishment can obtains the UE context, so thatthe RRC re-establishment can succeed and it is avoided that the UEreturns to the idle mode, data is lost and service continuity isguaranteed.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 is a schematic diagram illustrating a current structure for asystem of system architecture evolution (SAE);

FIG. 2 is a deployment scenario of small cell enhancement;

FIG. 3 is a schematic diagram illustrating a first method for supportingUE fast recovery in accordance with an embodiment of the presentdisclosure;

FIG. 4 is a schematic diagram illustrating a process that a UE accessesa small cell in accordance with an embodiment of the present disclosure;

FIG. 5 is a schematic diagram illustrating a process of synchronizing UEcontext in a small cell cluster in accordance with an embodiment of thepresent disclosure;

FIG. 6 is a schematic diagram illustrating a process of updating UEcontext in one or more other base stations in a small cell cluster inaccordance with an embodiment of the present disclosure;

FIG. 7 is a schematic diagram illustrating a process of releasing UEcontext in one or more other base stations in a small cell cluster inaccordance with an embodiment of the present disclosure;

FIG. 8 is a schematic diagram illustrating a method that a base stationin a small cell cluster uses saved UE context in accordance with anembodiment of the present disclosure;

FIG. 9 is a schematic diagram illustrating a process of exchanginginformation of small cell clusters between two base stations inaccordance with an embodiment of the present disclosure;

FIG. 10 is a schematic diagram illustrating a process of exchanginginformation of small cell clusters between two base stations during aprocess of X2 handover in accordance with an embodiment of the presentdisclosure;

FIG. 11 is a schematic diagram illustrating a process of exchanginginformation of small cell clusters between two base stations during aprocess of S1 handover in accordance with an embodiment of the presentdisclosure;

FIG. 12 is a schematic diagram illustrating a second method forsupporting UE fast recovery in accordance with an embodiment of thepresent disclosure;

FIG. 13 is a schematic diagram illustrating a first method that a basestation obtains UE context from another base station;

FIG. 14 is a schematic diagram illustrating a second method that a basestation obtains UE context from another base station;

FIG. 15 is a schematic diagram illustrating a third method that a basestation obtains UE context from another base station;

FIG. 16 is a schematic diagram illustrating a fourth method that a basestation obtains UE context from another base station.

DETAILED DESCRIPTION

FIGS. 3 through 16, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged telecommunication technologies.

In order to make the technical scheme and advantages of the presentdisclosure clearer, the present disclosure is described in furtherdetail hereinafter with reference to accompanying drawings and examples.

When a UE moves in a small cell scenario, a failure can occur. In orderto enable the UE to be recovered fastly in a failure condition, thepresent disclosure provides two methods for supporting UE fast recoveryso as to avoid that the UE returns to an idle mode, avoid data loss andguarantee service continuity.

A main idea of a first method is that: when a UE accesses a serving basestation, the serving base station accessed by the UE performs UE contextsynchronization to one or more other base stations in a small cellcluster of the serving base station. Thus, when a failure occurs for theUE and the UE needs to re-establish an RRC connection, since a basestation which receives the RRC connection reestablishment requestmessage saves UE context information, the RRC re-establishment cansucceed.

A main idea of a second method is that: when a failure occurs for a UEand the UE needs to re-establish a RRC connection, a base station whichreceives the RRC connection reestablishment request message requests UEcontext from a base station lastly serving the UE before the failure, sothat an RRC re-establishment can succeed.

A common point of the above two methods are: a base station whichreceives the RRC connection reestablishment request message obtains UEcontext through adopting different methods. Thus, an RRCre-establishment can succeed. It is avoided that the UE returns to anidle mode and data is lost. Service continuity is guaranteed as well.

The two methods provided by the present disclosure are instructed indetail as follows.

FIG. 3 is a schematic diagram illustrating a first method for supportingUE fast recovery.

A small cell cluster is composed by some base stations of small cell. Anetwork can configure some base stations of small cell to compose thesmall cell cluster according to a geographical area. Alternatively,according to difference of a small cell accessed by the UE, the smallcell cluster can be composed by some base stations around a base stationof the small cell. When the UE accesses a base station of the small cellcluster, a serving base station accessed by the UE transmits UE contextto one or more other base stations in the small cell cluster.Afterwards, when the UE context updating occurs or the UE context needsto be released, the base station accessed by the UE notifies the one ormore other base stations in the small cell cluster to perform UE contextupdating or release. For example, according to FIG. 3, base station 1synchronizes UE context to base station 2 and base station 3.

In the above first method, a process that a UE accesses a small cell isshown in FIG. 4, and includes steps as follows:

In step 401, the UE accesses base station 1. Herein, it is assumed thatbase station 1 is a base station of a small cell, and base station 1 isincluded in a small cell cluster.

The process that the UE accesses base station 1 can be that: the UE ischanged from an idle mode to an active mode in a cell of base station 1.Alternatively the UE accesses the cell of base station 1 throughhandover (in this condition, base station 1 is a target base station ofthe handover).

In step 402, base station 1 transmits UE context to one or more otherbase stations in the small cell cluster, e.g., eNB2 and eNB3 as shown inFIG. 3.

The UE context includes one or more kinds of information as follows: UEsecurity context, ERAB information, Source MME information, anidentifier of the UE in a source MME

UE capability, a handover limitation list, and UE history information.

The UE context can also include a cell identifier of a cell accessed bythe UE in base station 1 (that is, a cell accessed by the UE in basestation 1). The UE context can also include frequency information of thecell accessed by the UE in base station 1. Alternatively, the cellidentifier can be an E-UTRAN Cell Global Identifier (ECGI). The UEcontext also includes the identifier of the UE in the cell accessed bythe UE in base station 1. The identifier of the UE can be CRNTI. The UEcontext can also include other UE context information, which is notlimited in the present disclosure.

In step 403, a base station receiving the UE context saves the UEcontext information.

It is described in an embodiment in FIG. 8 about how the base stationuses the saved UE context specifically.

A process that base station 1 transmits UE context to base station 2 istaken as an example, to illustrate the process that base station 1transmits the UE context to one or more other base stations in the smallcell cluster of base station 1. As shown in FIG. 5, the process includessteps as follows:

The process shown in FIG. 5 can occur during the process that a UE ischanged from an idle mode to an active mode, alternatively, can occurduring the process that the UE accesses base station 1 through handover.

In step 501, base station 1 transmits UE context information to basestation 2.

Base station 2 and base station 1 are in a same small cell cluster. Basestation 1 can obtain whether base station 2 is in the small cell clusterof base station 1 according to operator configuration (i.e.,configuration information). Alternatively, base station 1 can determinebase stations of several small cells around the cell according todifference of a cell accessed by the UE. And these base stations aretaken as base station 2. The UE context is transmitted to base station2. Alternatively, base station 1 can determine base stations in a smallcell cluster around base station 1 according to a UE measurement report,which are taken as base station 2. The UE context information istransmitted to base station 2. It should be noted that base station 1determines the base stations included in the small cell clusteraccording to a measurement report of a current UE. Alternatively, basestation 1 determines the base stations included in the small cellcluster according to measurement reports of several UEs in the currentcell. Alternatively, base station 1 can determine the base stationsincluded in the small cell cluster of base station 1 according to theoperator configuration (i.e., the configuration information).Afterwards, the base stations are filtered according to the measurementreport of the UE or measurement reports of a group of UEs. Thus, thebase stations in the small cell cluster are determined finally. In apractical application, the base stations in the small cell cluster aredetermined according to other factors, which is not limited in thepresent disclosure.

Content included in a transmission message of the UE context informationis same as that of step 402, which is not described repeated herein.

In step 502, base station 2 saves the UE context information in thetransmission message of the UE context information.

In step 503, base station 2 transmits a UE context informationconfirmation message to base station 1.

The present disclosure provides two ways that base station 2 respondsbases station 1, which includes that base station 2 transmits a responsemessage and base station 2 does not transmit the response message. Thus,step 503 in FIG. 5 is shown as a dotted line.

Base station 1 can transmit UE context information to base station 2 viaan X2 interface. Alternatively base station 1 can transmit UE contextinformation to base station 2 via core network through an S1 interface.

When receiving a UE context modification message from a MME, orreceiving an ERAB establishment message/an ERAB modification message/anERAB release message and so on for the UE from the MME, which indicatethat the UE context needs to be updated, base station 1 triggers aprocess of updating the UE context to one or more other base stations inthe small cell cluster, as shown in FIG. 6.

In step 601, base station 1 transmits an UE context information updatingmessage to base station 2.

The UE context information updating message includes updated UE contextinformation, also includes a cell identifier of a cell accessed by theUE in base station 1 and an identifier of the UE in the cell accessed bythe UE in base station 1. The identifier of the UE in the cell accessedby the UE in base station 1 can be CRNTI. The updated UE contextinformation can include one or more kinds of UE context informationdescribed in step 402.

In step 602, base station 2 saves the updated UE context information.

In step 603, base station 2 transmits a confirmation of updating the UEcontext information to base station 1.

The present disclosure also provides two ways that base station 2responds to base station 1, which includes base station 2 transmits aresponse message and base station 2 does not transmit the responsemessage. Thus, step 603 in FIG. 6 is shown as a dotted line.

Base station 1 can transmit UE context information to base station 2 viaan X2 interface. Alternatively base station 1 can transmit UE contextinformation to base station 2 via core network through an S1 interface.

When the UE is changed from an active mode to an idle mode in a cell ofbase station 1, or the UE moves out of the cell of base station 1, orthe UE moves out of the cell of base station 1 and a target cell is notin the small cell cluster of base station 1, base station 1 triggers aprocess of releasing UE context information to one or more other basestations in the small cell cluster of base station 1, as shown in FIG.7.

In step 701, base station 1 transmits a request message of releasing theUE context to base station 2. The message includes a cell identifier ofa cell accessed by the UE in base station 1 and an identifier of the UEin the cell accessed by the UE in base station 1. The identifier of theUE in the cell accessed by the UE in base station 1 can be CRNTI.

After receiving the request message of releasing the UE context, basestation 2 releases the UE context of the corresponding UE.

In step 702, base station 2 transmits a response message of releasingthe UE context to base station 1. Herein, the present disclosure alsoprovides two ways that base station 2 responds to base station 1, whichincludes that base station 2 transmits a response message and basestation 2 does not transmit the response message. Thus, step 702 in FIG.7 is shown as a dotted line.

Base station 1 can transmit UE context release message to base station 2via an X2 interface. Alternatively base station 1 can transmit UEcontext release message via core network to base station 2 through an S1interface.

As described above, a base station in a small cell cluster can save theUE context transmitted by one or more other base stations. A process howa base station saving the UE context uses the saved UE context isillustrated by combination with FIG. 8. As shown in FIG. 8, a processincludes steps as follows.

In step 801, when a failure occurs for a UE in base station 1, the UEtransmits an RRC connection re-establishment request message to basestation 2.

The RRC connection re-establishment request message includes a cellidentifier of a cell where the failure occurs for the UE. The cellidentifier can be a PCI. The RRC connection re-establishment requestmessage can also include frequency information of the cell where thefailure occurs. Alternatively, the cell identifier can be an ECGI. Themessage can also include an identifier of the UE in a cell where thefailure occurs for the UE. The identifier of the UE in the cell wherethe failure occurs for the UE can be a CRNTI.

In step 802, since base station 2 saves UE security context information,an RRC connection re-establishment succeeds. Base station 2 transmits anRRC re-establishment message to the UE.

In step 803, the UE transmits an RRC re-establishment completion messageto base station 2.

In step 804, base station 2 transmits a path switch request message to aMME serving the UE. Herein, base station 2 knows the MME serving the UEaccording to the UE context information.

Herein, base station 2 sends out messages in steps 802 and 804. There isnot an absolute order for these two messages.

In step 805, the MME transmits a path switch request confirmationmessage to base station 2.

The process of a control plane is described above. A behavior of a userplane is not limited. Some operation ways for the user plane areillustrated as follows, which can further reduce data loss, andguarantee business continuity.

A first way: when receiving a RRC re-establishment request message ofstep 801, base station 2 assigns an TEID and a transport layer addressfor uplink and/or downlink data forwarding, and transmits the TEID andthe transport layer address to base station 1.

For the downlink data forwarding, when determining the downlink dataforwarding, base station 2 assigns the TEID and the transport layeraddress for the downlink data forwarding, and transmits them to basestation 1. For the uplink data forwarding, when requesting the uplinkdata forwarding, base station 2 assigns the TEID and the transport layeraddress for the uplink data forwarding, and transmits them to basestation 1. Base station 1 determines whether to accept the uplink dataforwarding. Base station 2 transmits a cell identifier of a source cellof the UE (a serving cell when the UE is in base station 1), anidentifier of the UE in the source cell to base station 1. Base station1 starts to forward data of the UE to base station 2 according to thecell identifier and the identifier of the UE in the cell, which arereceived from base station 2, and user plane of the data forwardingassigned by base station 2. Base station 1 transmits data transmissioncontext to base station 2. The data transmission context includes a PDCPSN and a HFN. A downlink PDCP SN indicates a SN needed to be used for anext PDCP SDU. An uplink PDCP SN indicates a SN of a first lost PDCPSDU. The data transmission context can also include a reception state ofan uplink PDCP SDU. Base station 2 can only request data forwardingcarried by an acknowledge mode (AM) of a Radio link control protocol(RLC). In order to guarantee data transmission in order, base station 2can transmit the data received from base station 1 firstly, and thentransmit the data received from a core network for the UE.

A second way: according to a measurement report of a UE, at the sametime of transmitting downlink data to the UE, data is also transmittedto a neighbor base station of which a signal quality is good in a smallcell cluster. And corresponding data transmission context is alsotransmitted. When the UE has a re-establishment in base station 2, basestation 2 starts to transmit the downlink data to the UE according tothe data transmission context received from base station 1, and transmitthe corresponding uplink data packet to a core network.

A third way: a core network transmits data to some base stations in asmall cell cluster at the same time. Thus, base station 2 receives thedata from the core network, synchronously with base station 1.

According to a process shown in FIG. 8, it is guaranteed that a RRCconnection re-establishment of a UE successes, so that the UE does notreturn to an idle mode and data loss is reduced, user experience isimproved.

The present disclosure provides some methods to make two base stationsexchange information of small cell cluster of the two base stationsrespectively. The methods are respectively illustrated in detail asfollows.

FIG. 9 is a schematic diagram illustrating a first method for exchangingsmall cell cluster information between two base stations. The methodincludes:

In step 901, base station 1 transmits an X2 setup request message tobase station 2. The X2 setup request message includes information of asmall cell cluster of base station 1.

The information of the small cell cluster includes a list of basestations in the small cell cluster of base station 1. The list of thebase stations can be a list of base station identifiers, or a list ofbase station IP addresses, or a list of other information which canidentify the base stations. The information of the small cell clustercan be a small cell cluster identifier. Base station 2 saves thereceived information.

In step 902, base station 2 transmits an X2 setup response message tobase station 1. The X2 setup response message includes information of asmall cell cluster of base station 2.

The information of the small cell cluster includes a list of basestations in the small cell cluster of base station 2. The list of thebase stations can be a list of base station identifiers, or a list ofbase station IP addresses, or a list of other information which canidentify the base stations. The information of the small cell clustercan be a small cell cluster identifier. Base station 1 saves thereceived information.

A second method for exchanging small cell cluster information betweentwo base stations is that:

When there is no an X2 interface between base station 1 and base station2, the small cell cluster information in a method as shown in FIG. 9 istransmitted through a core network between base station 1 and basestation 2, i.e., through an S1 interface.

A third method for exchanging small cell cluster information between twobase stations is described hereinafter.

A cell in base station 2 broadcasts information of a small cell cluster.The information of the small cell cluster is same as that described instep 902. A UE accesses a cell in base station 1, reads broadcastinformation of the cell in base station 2, obtains the information ofthe small cell cluster of base station 2, and transmits the informationof the small cell cluster of base station 2 to base station 1. Through asimilar process, base station 2 can obtain information of a small cellcluster of base station 1.

A small cell cluster of base station 1 (cluster1) and a small cellcluster of base station 2 (cluster2) can be different. That is, one ormore base stations included in the small cell cluster of base station 1can be not exactly same as one or more base stations included in thesmall cell cluster of base station 2. Through the three methods above,base station 1 and base station 2 have already respectively obtainedinformation of small cell clusters of correspondent base stations. Whenthe UE is handed over from base station 1 to base station 2, basestation 2 is needed to synchronize the UE context to a base station incluster2 and release the UE context in a base station not in cluster2.During a process of handing over the UE from base station 1 to basestation 2, base station 1 is a source base station of handover, basestation 2 is a target base station of the handover. A small cell clusterof the source base station is referred to as a source small cellcluster, i.e., cluster1 hereinafter. A small cell cluster of the targetbase station is referred to as a target small cell cluster, i.e.,cluster2 hereinafter. The present disclosure provides three ways forsynchronizing the UE context.

A first synchronization way: base station 2 synchronizes UE context toone or more other base stations in cluster2, i.e., base station 2performs a process as shown in FIG. 5 for a base stations in cluster2.Base station 1 releases the UE context in a base station in cluster1,i.e., base station 1 performs a process as shown in FIG. 7 for the basestation in cluster1.

A second synchronization way: for a base station in both cluster1 andcluster2, base station 2 performs a process as shown in FIG. 6,transmits updated UE context to the base station. Corresponded with thismethod, during a process of handover preparation, a source base station(e.g., base station 1) transmits an identifier of a cell where a UElocates in base station 1 and an identifier of the UE in the cell ofbase station 1 to a target base station (e.g., base station 2). Amessage of requesting to update UE context from base station 2 includesthe identifier of the cell and the identifier of the UE. Thus, the basestation in both cluster1 and cluster2 can update the corresponding UEcontext according to a request of base station 2.

For a base station in cluster2 but not in cluster1, base station 2performs a process as shown in FIG. 5 to transmit the UE contextinformation to the base station. For a base station in cluster1 but notin cluster2, base station 1 performs a process as shown in FIG. 7 torelease the UE context in the base station.

A third synchronization way: for a base station in both cluster1 andcluster2, base station 2 performs a process as shown in FIG. 6 totransmit UE context updating to the base station. Corresponded to thismethod, during a process of handover preparation, a source base station(e.g., base station 1) transmits an identifier of a cell where a UElocates in base station 1 and an identifier of the UE in the cell ofbase station 1 to a target base station (e.g., base station 2). Arequest message of the UE context updating from base station 2 includesthe identifier of the cell and the identifier of the UE. Thus, the basestation in both cluster1 and cluster2 can update the corresponding UEcontext according to a request of base station 2. For a base station incluster2 but not in cluster1, base station 2 performs a process as shownin FIG. 5 to transmit UE context information to the base station. For abase station in cluster1 but not in cluster2, base station 2 performs aprocess as shown in FIG. 7 to release UE context of the UE in the basestation. Corresponded to this method, during the process of the handoverpreparation, the source base station (e.g., base station 1) transmitsthe identifier of the cell where a UE locates in base station 1 and theidentifier of the UE in the cell of base station 1 to the target basestation (e.g., base station 2). The request message of the UE contextupdating from base station 2 includes the identifier of the cell and theidentifier of UE. Thus, the base station in both cluster1 and cluster2can update the corresponding UE context according to the request of basestation 2.

In addition to the aforementioned methods, small cell clusterinformation can be exchanged between two base stations during an X2handover process or an S1 handover process, which are respectivelyinstructed as follows by combination with FIG. 10 and FIG. 11.

FIG. 10 is a method for exchanging information of small cell clustersbetween two base stations in a process of handing over a UE from asource base station to a target base station through X2 handover inaccordance with an embodiment of the present disclosure. The processincludes steps as follows.

In step 1001, the source base station transmits a handover requestmessage to the target base station. The message includes the informationof a small cell cluster of the source base station. Content included inthe information of the small cell cluster is same as that of step 901,which is not described repeatedly herein.

In step 1002, the target base station transmits a handover requestconfirmation message to the source base station.

Optionally, the message can include the information of a small cellcluster of the target base station. Content included in the informationof the small cell cluster is same as that of step 902, which is notdescribed repeatedly herein.

In step 1003, a current handover execution process is performed.

In step 1004, a current handover completion process is performed.

In step 1005, a process of synchronizing UE context in a new small cellcluster is performed. The target base station and the source basestation synchronize the UE context information in one or more other basestations according to the information of small cell clusters exchangedin step 1001 and/or step 1002. A specific synchronization way is same asdescription above, which is not described repeatedly herein.

It should be noted that a process of synchronizing the UE context instep 1005 can be in accordance with the information exchanged in step1001 and step 1002, which is performed as soon as handover completion.Alternatively, the information of the small cell cluster of base station2 may be not included in step 1002. After the handover completion, basestation 2 re-executes a measurement process for the UE. The informationof the small cell cluster of base station 2 is obtained in accordancewith the measurement of the UE. Afterwards, the process of synchronizingthe UE context is performed. When the process of synchronizing the UEcontext needs participation of base station 1, after obtaining theinformation of the small cell cluster of base station 2, base station 2can transmits a message to base station 1 to notify the information ofthe small cell cluster of base station 2 to base station 1.

FIG. 11 is a method for exchanging information of small cell clustersbetween two base stations during a process that a UE is handed over froma source base station to a target base station through S1 handover,which includes steps as follows:

In step 1101, the source base station transmits a handover requirementmessage to a MME. The message includes the information of a small cellcluster of the source base station. Content included in the informationof the small cell cluster is same as that of step 901, which is notdescribed repeatedly herein. The information of the small cell clustercan be included in a transparent container from the source base stationto the target base station.

In step 1102, the MME transmits the handover request message to thetarget base station. The message includes the information of the smallcell cluster of the source base station. The content included in theinformation of the small cell cluster is same as that of step 901, whichis not described repeatedly herein. The information of the small cellcluster can be included in the transparent container from the sourcebase station to the target base station.

In step 1103, the target base station transmits a handover requestconfirmation message to the MME.

Optionally, the message can include the information of the small cellcluster of the target base station. The content included in theinformation of the small cell cluster is same as that of step 902, whichis not described repeatedly herein. The information of the small cellcluster can be included in the transparent container from the targetbase station to the source base station.

In step 1104, the MME transmits a handover command message to the sourcebase station.

When the handover request confirmation message in step 1103 includes theinformation of the small cell cluster of the target base station, thehandover command message in this step also includes the information ofthe small cell cluster of the target base station. The content of thesmall cell cluster is same as that of step 902, which is not describedrepeatedly herein. The information of the small cell cluster can beincluded in the transparent container from the target base station tothe source base station.

In step 1105, a process of handover execution is performed.

In step 1106, a process of handover completion is performed.

In step 1107, a process of synchronizing UE context in a new small cellcluster is performed. The target base station and the source basestation synchronize the UE context according to small cell clusterexchanged in step 1101 and step 1102, and/or step 1103 and step 1104. Aspecific synchronization way is described as above, which is notdescribed repeatedly herein.

It should be noted that a process of synchronizing the UE context instep 1107 can be in accordance with the information exchanged from steps1101 to 1104, which is performed as soon as handover completion.Alternatively, the information of the small cell cluster of base station2 may be not included in steps 1103 and 1104. After the handovercompletion, base station 2 re-executes a measurement process for the UE.The information of the small cell cluster of base station 2 is obtainedin accordance with the measurement of the UE. Afterwards, the process ofsynchronizing the UE context is performed. When the process ofsynchronizing the UE context needs participation of base station 1,after obtaining the information of the small cell cluster of basestation 2, base station 2 can transmits the information to base station1 to notify the information of the small cell cluster of base station 2to base station 1. The message can be an X2 interface message,alternatively can be an S1 interface message.

A first method for supporting UE fast recovery is described specificallyin accordance with embodiments of the present disclosure. As shown inFIG. 12, a second method for supporting UE fast recovery is describedspecifically as follows in accordance with embodiments of the presentdisclosure. The method shown in FIG. 12 includes steps as follows.

In step 1201, when a failure occurs for a UE in base station 1, the UEperforms cell reselection, e.g., selecting cell 2 of base station 2, andtransmits a RRC re-establishment request message to base station 2.

The RRC re-establishment request message includes a cell identifier of acell where the failure occurs for the UE. The cell identifier can be aPCI. The RRC re-establishment message can also include frequencyinformation of the cell where the failure occurs. The cell identifiercan an ECGI alternatively. The message can also include an identifier ofthe UE in the cell where the failure occurs for the UE. The identifierof the UE in the cell where the failure occurs for the UE can be aCRNTI. The RRC connection re-establishment request message can alsoinclude a TAI of the cell where the failure occurs.

In step 1202, base station 2 obtains UE context from base station 1. Thebase station 1 or base station 2 can perform access check for the UE.Base station 1 can also perform security check for the UE. Inparticular, there are four methods that base station 2 obtains the UEcontext from base station 1 and base station 1 or base station 2performs the access check respectively as shown in FIG. 13, FIG. 14,FIG. 15 and FIG. 16. It is also introduced in FIG. 13, FIG. 14, FIG. 15and FIG. 16 that base station 1 performs the security check for the UE.

Afterwards, base station 1 stops transmitting downlink data for the UE,and forwards the data to base station 2.

The first method is shown in FIG. 13, which includes the followingsteps. Base station 2 transmits a UE information request message to basestation 1 to request UE context information. The message includes thecell identifier of the cell (the cell in base station 1) where thefailure occurs for the UE. The cell identifier can be the PCI. Themessage can also include frequency information of the cell where thefailure occurs. The cell identifier can include the ECGI alternatively,or include the PCI and the ECGI at the same time. The message alsoincludes the identifier of the UE in the cell where the failure occursfor the UE. The identifier of the UE in the cell where the failureoccurs for the UE can be the CRNTI. The identifier of the UE in the cellwhere the failure occurs for the UE can be an eNB X2 AP ID of the UE inthe source base station alternatively. The message can also include ashort Media Access Control (MAC) identifier (shortMACI).

The message also includes the cell identifier PCI and/or ECGI of are-establishment cell. The message also includes eNB X2 AP ID assignedin an interface between eNB1 and eNB2 for the UE by eNB2.

In step 1302, base station 1 performs security check, access check forthe UE, and performs PLMN selection.

A method that base station 1 performs the security check for the UEincludes that: performing the security check for the UE by use of thePCI or the ECGI of the cell where the failure occurs and obtained fromstep 1301, CRNTI of the UE in the cell where the failure occurs and theshortMACI. Base station 1 finds the cell where the failure occursaccording to the PCI of the cell where the failure occurs. In order toavoid PCI confusion, base station 1 can find the cell where the failureoccurs according to the ECGI of the cell where the failure occurs or PCIand frequency information of the cell where the failure occurs. Basestation 1 finds the UE context according to CRNTI of the UE in the cellwhere the failure occurs. Base station 1 computes the shortMACIaccording to cell identifier PCI of the re-establishment cell andsecurity context in the UE context. If the shortMACI computed and theshortMACI received from base station 1 are same, the UE passes thesecurity check. Otherwise, the UE does not pass the security check. eNB1transmits UE information failure to eNB2 in step 1303.

A method that base station 1 performs the access check for the UEincludes: performing the access check for the UE according to the cellidentifier of the re-establishment cell and UE handover restriction list(HRL). Base station 1 determines whether PLMN IDs broadcasted in there-establishment cell includes a registered PLMN (rPLMN) ID or anequivalent PLMN (ePLMN) ID of the UE, determines whether there-establishment cell is not in a tracking area (TA) prohibited for theUE and determines whether the re-establishment cell is not in a radioaccess technology (RAT) prohibited for the UE. Base station 1 can obtainthe cell identifier of the cells in base station 2, a TAC supported bythe cells in base station 2 and a PLMN ID list of the cells in basestation 2 through X2 setup procedure. Afterwards, base station 1 knows aPLMN ID list broadcasted by the reestablish cell in base station 2 andthe TA (TAC or TAI) where the reestablish cell in base station 2 locatesaccording to the PCI or the ECGI of the reestablish cell in base station2 received in step 1301 and information obtained during X2 setup. Themessage in step 1301 can include the TA (TAC or TAI) of there-establishment cell and the broadcasted PLMN ID list. If the PLMN IDsbroadcasted by the re-establishment cell does not include the rPLMN orthe ePLMN of the UE, or the re-establishment cell is included in aprohibited TA, or the re-establishment cell is included in a prohibitedRAT for the UE, the access check fails. Otherwise, the access checksuccesses. Base station 1 knows the RAT to which the re-establishmentcell belongs according to frequency of the re-establishment cell orconfiguration. If the access check fails, eNB1 transmits UE informationfailure to eNB2 in step 1303. In the condition that the access checksuccesses, base station 1 selects a serving PLMN in one or more PLMNsbroadcasted by the re-establishment cell and the PLMN ID is rPLMN ID orePLMN ID of the UE. Base station 1 takes the newly-selected PLMN as therPLMN, and takes the previous rPLMN and other ePLMNs as ePLMNs that areput in a HRL. The new HRL is transmitted to base station 2 in step 1304.

In step 1303, according to a result of the security check and a resultof the access check in step 1302, in the condition that both thesecurity check and the access check succeed, eNB1 transmits a UEinformation response to eNB2, in the condition that either the securitycheck or the access check fails, eNB1 transmits a UE information failureto base station 2.

The UE information response or the UE information failure includes aneNB UE S1 AP assigned for the UE by eNB2. The UE information responsecan also include an eNB UE X2 AP assigned for the UE by eNB1. The UEinformation failure can also include a failure reason, e.g., a maliciousUE or prohibited access.

In another method, in the condition that both the security check and theaccess check success, eNB1 can transmit a message in step 1304 directly.In the condition that check fails, eNB1 does not transmit the message toeNB2. eNB2 knows that the UE information request fails according to animplementation way such as a timer. Thus, a RRC re-establishment rejectmessage is transmitted to the UE in step 1203.

In step 1304, eNB1 transmits a handover request message to eNB2. Themessage can include eNB UE X2 AP ID assigned for the UE by eNB2. Anidentifier of a target cell in the handover request message is the ECGIof the re-establishment cell received from base station 2 in step 1301.The security information in the handover request message is computedaccording to the PCI and the frequency of the re-establishment cell.eNB1 can obtain the frequency of the re-establishment cell during theprocess of establishing X2 between eNB1 and eNB2. Alternatively, thefrequency of the re-establishment cell can be included in step 1301.

In step 1305, eNB2 transmits a handover request confirmation message toeNB1.

In a re-establishment scenario, the handover request confirmationmessage may not include a transparent container from a target basestation to a source base station.

Steps 1305 and 1203 are transmitted by eNB2. There are no absolute orderbetween steps 1305 and 1203, which is not limited in the presentdisclosure.

It should be noted that, in the condition that there is no X2 interfacebetween base station 2 and base station 1, the messages of steps1301-1305 can be transmitted via a S1 interface. When base station 2transmits the UE information request to base station 1 in the S1interface via an MME, the UE information request includes the TAI andthe ECGI of the cell where the failure occurs received from the UE instep 1201. TAI is used for routing among core networks and finding theMME with which base station 1 connects. The MME connected with basestation 1 finds base station 1 by use of the ECGI of the cell where thefailure occurs.

A second method is as shown in FIG. 14, which in detail includes thefollowing steps.

Steps 1401 and 1402 are respectively the same as steps 1301 and 1302,which is not described repeatedly herein. It should be noted that, inthe condition that either the access check or the security check failsin step 1402, base station 1 transmits the UE information failure tobase station 2 in step 1403.

In step 1403, according to a result of security check and a result ofaccess check in step 1402, in the condition that both the security checkand the access check success, eNB1 transmits a UE information responseto eNB2. In the condition that either the security check or the accesscheck fails, eNB1 transmits a UE information failure to base station 2.

The UE information failure includes eNB UE S1 AP ID assigned for the UEby eNB2. The UE information failure can also include a failure reason,e.g., a malicious UE or prohibited access.

The UE information response includes eNB UE S1 AP ID assigned for the UEby eNB2. The UE information response can also include eNB UE X2 AP IDassigned for the UE by eNB1.

The UE information response message includes the UE context information.The UE context information includes one or more kinds of information asfollows: UE security context, ERAB information, Source MME information,an identifier of a UE in a source MME, UE capability, a handoverlimitation list, and UE history information.

The ERAB information includes an ERAB identifier, ERAB QoS information,an ERAB uplink GTP TED, whether downlink data forwarding is needed.

The UE context can also include the cell identifier of the cell where afailure occurs for the UE in base station 1. The cell identifier can bethe PCI. The UE context can also include frequency information of thecell where the failure occurs. The cell identifier can be the ECGIalternatively. The UE context also includes the identifier of the UE inthe cell where the failure occurs for the UE in base station 1. Theidentifier of the UE can be the CRNTI or eNB X2 AP ID of the UE in thesource base station. The UE context information can also include otherUE context information, which is not limited in the present disclosure.

The UE context information also includes SN status information. The SNstatus information includes a PDCP SN and HFN status information. Indetail, the SN status information includes receiving status of an uplinkPDCP SDU of the ERAB that data forwarding is needed and a COUNT value ofuplink and downlink. The COUNT value refers to the PDCP SN and HFNinformation. A downlink PDCP SN indicates an SN needed to be used for anext PDCP SDU. An uplink PDCP SN indicates a SN of a first lost PDCPSDU. Base station 2 can only request uplink data forwarding carriedthrough a RLC acknowledge mode (AM). In order to ensure datatransmission in order, base station 2 can transmits the data receivedfrom base station 1 to the UE firstly, and then transmits the datareceived from the core network to the UE. Base station 1 can transmitthe SN status information to base station 2 through the UE informationresponse message, alternatively transmit it through another separatemessage.

Base station 1 stops transmitting downlink data to the UE.

In step 1404, base station 2 allocates resource for the REAB. Basestation 2 transmits a UE information indication to base station 1. TheUE information indication can be a confirmation message of step 1403,can also be an independent indication message. The message includes eNBUE X2 AP ID assigned by eNB1 and eNB2.

The message can also include an accepted ERAB list. The accepted ERABlist includes a downlink and/or uplink GTP TED for data forwarding. Themessage can also include an ERAB list not accepted.

After receiving the message, base station 1 can start forwarding data tobase station 2.

Steps 1404 and 1203 are transmitted by base station 2. There is noabsolute order between 1404 and 1203, which is not limited in thepresent disclosure.

It should be noted that, in the condition that there is no X2 interfacebetween base station 2 and base station 1, the messages of steps1401-1404 can be transmitted via a S1 interface. When base station 2transmits the UE information request to base station 1 in the S1interface via an MME, the UE information request includes the TAI andthe ECGI of the cell where the failure occurs received from the UE instep 1201. TAI is used for routing among core networks and finding theMME with which base station 1 connects. The MME connected with basestation 1 finds base station 1 by use of the ECGI of the cell where thefailure occurs.

A third method is as shown in FIG. 15, which includes the followingsteps.

Step 1501 is the same as step 1301, which is not described repeatedlyherein.

In step 1502, base station 1 performs security check for the UE. Basestation 1 performs the security check for the UE by use of the PCI orthe ECGI of the cell where the failure occurs and obtained from step1501, the CRNTI of the UE in the cell where the failure occurs, theshortMACI. Base station 1 finds the cell where the failure occursaccording to the PCI of the cell where the failure occurs. In order toavoid PCI confusion, base station 1 finds the cell where the failureoccurs according to the ECGI of the cell where the failure occurs or PCIand frequency information of the cell where the failure occurs receivedin step 1501. Base station 1 finds the UE context according to the CRNTIof the UE in the cell where the failure occurs. Base station 1 computesthe shortMACI according to cell identifier PCI of the re-establishmentcell and security context in the UE context. If the shortMACI computedand the shortMACI received from base station 1 are same, the UE passesthe security check. Otherwise, the UE does not pass the security check.

In the condition that the security check successes, base station 1transmits a handover request message to base station 2 in step 1503.

In the condition that security check fails, base station 1 does nottransmit the message in step 1503. eNB2 knows that the UE informationrequest fails according to an implementation way, e.g., a timermechanism. Thus, a RRC re-establishment reject message is transmitted tothe UE in step 1203.

In another method, the security check can also be performed after basestation 2 receives the handover request message in step 1504. Thus, thisstep can be skipped. Corresponding to this way, the handover requestmessage in step 1503 can include the security context of the UE in thecell where the failure occurs. Base station 2 computes the shortMACIaccording to cell identifier PCI of the re-establishment cell and thesecurity context in the UE context received from base station 1. If theshortMACI computed and the shortMACI received from the UE in step 1201are same, the UE passes the security check. Otherwise, the UE does notpass the security check. Base station 2 transmits RRC Re-establishmentreject to UE in step 1203.

In step 1503, eNB1 transmits the handover request message to eNB2. Themessage can include eNB UE X2 AP ID assigned for the UE by eNB2. Anidentifier of a target cell in the handover request message is the ECGIof the re-establishment cell received from base station 2 in step 1301.The security information in the handover request message is computedaccording to the PCI and the frequency of the re-establishment cell.eNB1 can obtain the frequency of the re-establishment cell during theprocess of establishing X2 between eNB1 and eNB2. Alternatively, thefrequency of the re-establishment cell can be included in step 1301.

Base station 1 transmits HRL information of the UE to base station 2.

In step 1504, base station 2 performs access check for the UE. Basestation 2 performs the access check according to a cell identifier ofthe re-establishment cell and HRL of the UE. Base station 2 determineswhether the PLMN IDs broadcasted by the re-establishment cell includesan rPLMN ID or an ePLMN ID of the UE, whether the re-establishment cellis not included in the prohibited TA, and whether the re-establishmentcell is not included in the prohibited RAT. If the PLMN IDs broadcastedby the re-establishment cell doesn't include the rPLMN ID or the ePLMNID of the UE, or the re-establishment cell is included in the prohibitedTA, or the re-establishment cell is included in the prohibited RAT, theaccess inspection fails. Otherwise, the access check successes. If theaccess check fails, eNB2 transmits a handover preparation failure instep 1505. In the condition that access check successes, base station 2selects a serving PLMN in the PLMN IDs broadcasted by there-establishment cell and the PLMN ID is the rPLMN ID or ePLMN ID of theUE. Base station 2 takes the newly-selected PLMN as the rPLMN, and takesthe previous rPLMN and other ePLMNs as ePLMNs that are put in a HRL.Base station 2 put the newly-selected PLMN ID in the TAI, and transmitsthe TAI to the MME in step 1206.

In step 1505, eNB2 transmits a handover request confirmation message toeNB1. In the condition that the access check successes, or the accesscheck and the security check success, eNB2 transmits the handoverrequest confirmation message to eNB1.

In a re-establishment scenario, the handover request confirmationmessage may not include a transparent container from a target basestation to a source base station.

Steps 1505 and 1203 are transmitted by eNB2. There is no absolute orderbetween step 1305 and step 1203, which is not limited in the presentdisclosure.

It should be noted that, in the condition that there is no X2 interfacebetween base station 2 and base station 1, the messages of steps1501-1505 can be transmitted via a S1 interface. When base station 2transmits the UE information request to base station 1 in the S1interface via an MME, the UE information request includes the TAI andECGI of the cell where the failure occurs that is received from the UEin step 1201. TAI is used for routing among core networks and findingthe MME with which base station 1 connects. The MME connected with basestation 1 finds base station 1 by use of the ECGI of the cell where thefailure occurs.

A forth method is as shown in FIG. 16, which includes the followingsteps.

In step 1601, base station 2 transmits a radio link failure indicationmessage to base station 1. The message includes a PCI of the cell wherethe failure occurs, a C-RNTI of the UE in the cell where the failureoccurs, a shortMAC-I received from UE in RRC connection re-establishmentrequest message and an ECGI of a re-establishment cell. The message canalso include the ECGI of the cell where the failure occurs. The messagecan also include an indicator whether base station 2 requests UEcontext. In the condition that base station 2 has not the UE context,the message includes an indicator of requesting the UE context. In thecondition that base station 2 includes the indicator of requesting theUE context, a RRC connection re-establishment reject message is nottransmitted to the UE for the moment. After a message in step 1603 isreceived, a message in step 1203 is transmitted to the UE.Alternatively, in the condition that the message in step 1603 is notreceived, the RRC connection re-establishment reject message istransmitted to the UE.

In step 1602, base station 1 performs security check, access check forthe UE, and performs PLMN selection.

When the radio link failure indication message received by base station1 includes the indicator of requesting the UE context, base station 1performs the security check, the access check for the UE, and performsthe PLMN selection.

Base station 1 knows the PCI of the re-establishment cell, supportedPLMN ID(s), a TAC and frequency information according to the ECGI of there-establishment cell received from base station 2 and an ECGI, a PCI, asupported PLMN ID(s) and a TAC of a serving cell in base station 2obtained during the process of establishing a X2 interface.

A method that base station 1 performs the security check for the UE isthat: base station 1 performs the security check for the UE by use ofthe PCI or the ECGI of the cell where the failure occurs and obtainedfrom step 1601, CRNTI of the UE in the cell where the failure occurs andthe shortMACI. Base station 1 can find the cell where the failure occursaccording to the PCI of the cell where the failure occurs. In order toavoid PCI confusion, base station 1 can find the cell where the failureoccurs according to the ECGI of the cell where the failure occursreceived in step 1601 or PCI and the frequency information of the cellwhere the failure occurs. Base station 1 finds the UE context accordingto the CRNTI of the UE in the cell where the failure occurs. Basestation 1 computes the shortMACI according to cell identifier PCI of there-establishment cell and security context in the UE context. If theshortMACI computed and the shortMACI received from base station 1 aresame, the UE passes the security PCI or. Otherwise, the UE does not passthe security PCI.

A method that base station 1 performs the access PCI or for the UE isthat: base station 1 performs the access PCI or according to the cellidentifier of the re-establishment cell and a HRL of the UE. Basestation 1 determines whether PLMN IDs broadcasted in there-establishment cell includes a registered PLMN (rPLMN) ID or anequivalent PLMN (ePLMN) ID, determines whether the re-establishment cellis not in a tracking area (TA) prohibited for the UE and determineswhether the re-establishment cell is not in a radio access technology(RAT) prohibited for the UE. Base station 1 can obtain the cellidentifier of the cell in base station 2, a TAC supported by the cell inbase station 2 and a PLMN ID list of the cell in base station 2 throughX2 setup procedure. Afterwards, base station 1 knows a PLMN ID listbroadcasted by the cell in base station 2 and the TA where the cell inbase station 2 locates according to the PCI or the ECGI of the cell inbase station 2 received in step 1601 and information obtained during X2setup procedure. The message in step 1601 can include the TA (TAC orTAI) of the re-establishment cell and the broadcasted PLMN ID list. Ifthe PLMN ID broadcasted by the re-establishment cell does not includethe rPLMN or the ePLMN of the UE, or the re-establishment cell isincluded in a prohibited TA, or the re-establishment cell is included ina prohibited RAT for the UE, the access check fails. Otherwise, theaccess check successes. Base station 1 knows the RAT to which there-establishment cell belongs according to frequency of there-establishment cell or configuration. In the condition that the accesscheck successes, base station 1 selects a serving PLMN in one or morePLMN IDs broadcasted by the re-establishment cell and the PLMN ID is therPLMN ID or ePLMN ID of the UE. Base station 1 takes the newly-selectedPLMN as the rPLMN, and takes the previous rPLMN and other ePLMNs asePLMNs that are put in a HRL. The new HRL is transmitted to base station2 in step 1603.

In the condition that the security check and the access check success,base station 1 transmits the handover request message in step 1603 tobase station 2.

In the condition that either the security check or the access checkfails, base station 1 does not transmits the message in step 1603. eNB2knows UE context request failure according to an implementation way,e.g., a timer mechanism. Thus, the RRC connection reject message istransmitted to the UE in step 1203.

In another method, the security check can also be performed after basestation 2 receives the handover request message from base station 1 instep 1603. Thus, security check in this step can be skipped.Corresponding to this way, the handover request message in step 1603 caninclude the security context of the UE in the cell where the failureoccurs. Base station 2 computes the shortMACI according to cellidentifier PCI of the re-establishment cell and the security context inthe UE context received from base station 1. If the shortMACI computedand the shortMACI received from the UE in step 1201 are same, the UEpasses the security check. Otherwise, the UE does not pass the securitycheck. Base station 2 transmits the RRC connection re-establishmentreject message to UE in step 1203.

In step 1603, eNB1 transmits the handover request message to eNB2.

In another method, the message in step 1601 may not include theindicator of requesting the UE context. If the message in step 1601includes a RRC connection establishment indicator to indicate that theradio link failure is triggered by RRC connection establishment, basestation 1 does not need to transmit the message in this step. If theradio link failure indicator is triggered by the RRC connectionre-establishment and base station 1 has not perform handover preparationto the re-establishment cell in base station 2, base station 1 cantrigger the process in the step.

The target cell identifier in the handover request message is the ECGIof the re-establishment cell received from base station 2 in step 1601.The security information in the handover request message is computedaccording to the PCI and the frequency of the re-establishment cell.eNB1 can obtain the frequency of the re-establishment cell during theprocess of establishing a X2 interface between eNB1 and eNB2.Alternatively, the frequency of the re-establishment cell is included instep 1301.

Base station 1 transmits the HRL information of the UE to base station2.

In step 1604, eNB2 transmits a handover request confirmation message toeNB1. In the condition that resource in eNB2 is not enough or otherabnormal conditions, base station 2 can transmit a handover preparationfailure message to base station 1. In this condition, a RRC connectionre-establishment reject message is transmitted to the UE in step 1203.

For the re-establishment scenario, the handover request confirmationmessage may not include a transparent container from a target basestation to a source base station.

Base station 2 implements step 1604 and 1203. There is no absolute orderbetween step 1604 and step 1203, which is not limited in the presentdisclosure.

It should be noted that, in the condition that there is no X2 interfacebetween base station 2 and base station 1, the messages of steps1601-1604 can be transmitted via a S1 interface. When base station 2transmits the radio link failure indicator to base station 1 in the S1interface via an MME, the radio link failure indicator includes the TAIand the ECGI of the cell where the failure occurs received from the UEin step 1201. TAI is used for routing among core networks and findingthe MME with which base station 1 connects. The MME connected with basestation 1 finds base station 1 by use of the ECGI of the cell where thefailure occurs.

In step 1203, base station 2 transmits a RRC connection re-establishmentmessage to the UE. If the access check or the security check fails forthe UE in step 1202, base station 2 transmits a RRC connectionre-establishment reject message to the UE in this step.

In step 1204, the UE transmits a RRC connection re-establishmentcomplete message to base station 2. In the condition of receiving theRRC connection re-establishment message in step 1203, the UE transmitsthe RRC connection re-establishment complete message to base station 2.

In step 1205, a process of RRC connection reconfiguration between basestation 2 and the UE is performed. Base station 2 transmits a RRCconnection reconfiguration message to the UE. The UE transmits a RRCconnection reconfiguration complete message to base station 2.

In step 1206, base station 2 transmits a path switch request message toa MME serving the UE to request that the core network hands over adownlink user plane. Herein, base station 2 obtains the MME serving theUE according to the UE context information received from base station 1in step 1202.

In step 1207, the MME transmits a downlink path switch response messageto base station 2.

In both steps 1206 and 1203, base station 2 sends out messages. There isnot an absolute order for the two messages themselves, which is notlimited in the present disclosure.

In step 1208, base station 2 requests resource release to base station1. In the present disclosure, the method can include or not include thestep. If the step is not performed, after base station 1 has no data tobe forwarded and receives end marker from a MME, resource assigned forthe UE and UE context are released. If the step is performed, after basestation 1 receives the message, has no the data to be forwarded and basestation 1 receives the end marker from the MME, the resource assignedfor the UE and the UE context are released.

So far, the process for the method as shown in FIG. 12 ends.

Although the present disclosure has been described with an exemplaryembodiment, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method performed by a base station in awireless communication system, the method comprising: receiving a firstradio resource control (RRC) message from a user equipment (UE);transmitting a UE context request message associated with the UE to alast serving base station; receiving a UE context response messageassociated with the UE from the last serving base station; transmittinga path switch request message to a mobility management node associatedwith the UE based on the UE context response message; receiving a pathswitch response message from the mobility management node associatedwith the UE; and transmitting information associated with releasing acontext of the UE to the last serving base station based on the pathswitch response message, wherein the UE context request message includesa base station UE application protocol (AP) identifier allocated by thebase station, and wherein the UE context response message includes thebase station UE AP identifier allocated by the base station and a basestation UE AP identifier allocated by the last serving base station. 2.The method of claim 1, wherein the UE context request message includesat least one of a cell identifier of the base station, or a short MediaAccess Control (MAC) identifier (shortMACI).
 3. The method of claim 2,wherein a security check is performed by the last serving base stationbased on the shortMACI included in the UE context request message, andwherein a resource allocated for the UE and the context of the UE isreleased based on the information associated with releasing the contextof the UE.
 4. The method of claim 1, wherein the UE context responsemessage includes at least one of information associated with themobility management node, security information of the UE, capabilityinformation of the UE, or a mobility restriction list.
 5. A base stationin a wireless communication system, the base station comprising: atransceiver; and a controller coupled with the transceiver andconfigured to: receive a first radio resource control (RRC) message froma user equipment (UE), transmit a UE context request message associatedwith the UE to a last serving base station, receive a UE contextresponse message associated with the UE from the last serving basestation, transmit a path switch request message to a mobility managementnode associated with the UE based on the UE context response message,receive a path switch response message from the mobility management nodeassociated with the UE, and transmit information associated withreleasing a context of the UE to the last serving base station based onthe path switch response message, wherein the UE context request messageincludes a base station UE application protocol (AP) identifierallocated by the base station, and wherein the UE context responsemessage includes the base station UE AP identifier allocated by the basestation and a base station UE AP identifier allocated by the lastserving base station.
 6. The base station of claim 5, wherein the UEcontext request message includes at least one of a cell identifier ofthe base station, or a short Media Access Control (MAC) identifier(shortMACI).
 7. The base station of claim 6, wherein a security check isperformed by the last serving base station based on the shortMACIincluded in the UE context request message, and wherein a resourceallocated for the UE and the context of the UE is released based on theinformation associated with releasing the context of the UE.
 8. The basestation of claim 5, wherein the UE context response message includes atleast one of information associated with the mobility management node,security information of the UE, capability information of the UE, or amobility restriction list.
 9. A method performed by a last serving basestation in a wireless communication system, the method comprising:receiving a user equipment (UE) context request message associated witha UE from a base station; performing a security check based on the UEcontext request message associated with the UE; transmitting a UEcontext response message associated with the UE to the base stationbased on a success of the security check; and receiving informationassociated with releasing a context of the UE from the base station,wherein the UE context request message includes a base station UEapplication protocol (AP) identifier allocated by the base station, andwherein the UE context response message includes the base station UE APidentifier allocated by the base station and a base station UE APidentifier allocated by the last serving base station.
 10. The method ofclaim 9, wherein the UE context request message includes at least one ofa cell identifier of the base station, or a short Media Access Control(MAC) identifier (shortMACI).
 11. The method of claim 10, wherein a pathswitch request message is transmitted from the base station to amobility management node associated with the UE based on the UE contextresponse message, wherein a path switch response message is received atthe base station from the mobility management node associated with theUE, wherein the information associated with releasing the context of theUE is transmitted from the base station based on the path switchresponse message, wherein the security check is performed by the lastserving base station based on the shortMACI included in the UE contextrequest message, and wherein a resource allocated for the UE and thecontext of the UE is released based on the information associated withreleasing context of the UE.
 12. The method of claim 9, wherein the UEcontext response message includes at least one of information associatedwith a mobility management node, security information of the UE,capability information of the UE, or a mobility restriction list.
 13. Alast serving base station in a wireless communication system, the lastserving base station comprising: a transceiver; and a controller coupledwith the transceiver and configured to: receive a user equipment (UE)context request message associated with a UE from a base station,perform a security check based on the UE context request messageassociated with the UE, transmit a UE context response messageassociated with the UE to the base station based on a success of thesecurity check, and receive information associated with releasing acontext of the UE from the base station, wherein the UE context requestmessage includes a base station UE application protocol (AP) identifierallocated by the base station, and wherein the UE context responsemessage includes the base station UE AP identifier allocated by the basestation and a base station UE AP identifier allocated by the lastserving base station.
 14. The last serving base station of claim 13,wherein the UE context request message includes at least one of a cellidentifier of the base station, or a short Media Access Control (MAC)identifier (shortMACI).
 15. The last serving base station of claim 14,wherein a path switch request message is transmitted from the basestation to a mobility management node associated with the UE based onthe UE context response message, wherein a path switch response messageis received at the base station from the mobility management nodeassociated with the UE, wherein the information associated withreleasing the context of the UE is transmitted from the base stationbased on the path switch response message, wherein the security check isperformed by the last serving base station based on the shortMACIincluded in the UE context request message, and wherein a resourceallocated for the UE and the context of the UE is released based on theinformation associated with releasing context of the UE.
 16. The lastserving base station of claim 13, wherein the UE context responsemessage includes at least one of information associated with a mobilitymanagement node, security information of the UE, capability informationof the UE, or a mobility restriction list.
 17. A method performed by auser equipment (UE) in a wireless communication system, the methodcomprising: transmitting a first radio resource control (RRC) message toa base station; and receiving a last serving RRC message associated withan RRC connection from the base station, wherein a UE context requestmessage associated with the UE is transmitted from the base station to alast serving base station based on reception of the first RRC message,wherein the last serving RRC message associated with the RRC connectionis transmitted from the base station, based on reception of a UE contextresponse message associated with the UE at the base station, wherein theUE context request message includes a base station UE applicationprotocol (AP) identifier allocated by the base station, and wherein theUE context response message includes the base station UE AP identifierallocated by the base station and a base station UE AP identifierallocated by the last serving base station.
 18. The method of claim 17,wherein the UE context request message includes at least one of a cellidentifier of the base station, or a short Media Access Control (MAC)identifier (shortMACI).
 19. The method of claim 17, wherein the UEcontext response message includes at least one of information associatedwith a mobility management node, security information of the UE,capability information of the UE, or a mobility restriction list.
 20. Auser equipment (UE) in a wireless communication system, the UEcomprising: a transceiver; and a controller configured to: transmit afirst radio resource control (RRC) message to a base station, andreceive a last serving RRC message associated with an RRC connectionfrom the base station, wherein a UE context request message associatedwith the UE is transmitted from the base station to a last serving basestation based on reception of the first RRC message, wherein the lastserving RRC message associated with the RRC connection is transmittedfrom the base station, based on reception of a UE context responsemessage associated with the UE at the base station, wherein the UEcontext request message includes a base station UE application protocol(AP) identifier allocated by the base station, and wherein the UEcontext response message includes the base station UE AP identifierallocated by the base station and a base station UE AP identifierallocated by the last serving base station.
 21. The UE of claim 20,wherein the UE context request message includes at least one of a cellidentifier of the base station, or a short Media Access Control (MAC)identifier (shortMACI).
 22. The UE of claim 20, wherein the UE contextresponse message includes at least one of information associated with amobility management node, security information of the UE, capabilityinformation of the UE, or a mobility restriction list.